Skip to content

Conversation

@ErikWegner
Copy link

Run into a stuck multipart parsing (in axum), because a request had two boundaries within the header like this:

Content-Type: multipart/form-data; boundary=---------------------------17832986845363619572950809769; boundary=------------------------bjsYDym0V6iqcnC7ILHUdu

The parser used the first value and never succeeded in finding a part, it did even blocked the whole connection.

This change detects multiple values for boundary and prevents a dead lock.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant